Network slice selection in a mobile communication network

ABSTRACT

Apparatuses, methods, and systems are disclosed for selecting a network slice. One apparatus includes a processor and a transceiver that communicates with a mobile communication network supporting a plurality of application categories. The processor receives a request to send a data packet, wherein the data packet is generated by an application of the apparatus. The processor identifies a network slice selection indicator associated with the application of the apparatus and transmits the data packet via a network connection to a network slice in the mobile communication network, wherein the network connection is associated with the identified network slice selection indicator.

CROSS-REFERENCE TO RELATED APPLICATIONS

This is a continuation application of and claims priority to U.S. patentapplication Ser. No. 15/967,330 entitled “Supporting Network Slicing ina Wireless Communication System” and filed on Apr. 30, 2018 forApostolis Salkintzis, which is incorporated herein by reference, and toU.S. patent application Ser. No. 15/050,840 entitled “Procedures toSupport Network Slicing in a Wireless Communication System” and filed onFeb. 23, 2016 for Apostolis Salkintzis, which is also incorporatedherein by reference.

FIELD

The subject matter disclosed herein relates generally to wirelesscommunications and more particularly relates to selecting a networkslice in a mobile communication network.

BACKGROUND

The following abbreviations are herewith defined, at least some of whichare referred to within the following description.

3GPP Third Generation Partnership Project

ANDSF Access Network Discovery and Selection Function

AP Access Point

APN Access Point Name

AS Access Stratum

CIoT Cellular Internet of Things

DCN Dedicated Core Network

DL Downlink

eNB Evolved Node B

EPC Evolved Packet Core

ETSI European Telecommunications Standards Institute

H-PLMN Home Public Land Mobile Network

HSS Home Subscriber Server

IMS IP Multimedia Subsystem

IP Internet Protocol

IoT Internet of Things

ISP Internet Service Provider

LAN Local Area Network

LTE Long Term Evolution

MBB Mobile Broadband

MME Mobility Management Entity

MMS Multimedia Messaging Service

MTC Machine-Type Communications

NAS Non-Access Stratum

NFV Network Function Virtualization

OFDM Orthogonal Frequency Division Multiplexing

PDCP Packet Data Convergence Protocol

PDU Protocol Data Unit

PGW Packet Data Network Gateway

PLMN Public Land Mobile Network

RAN Radio Access Network

RCS Rich Communication Services

RRC Radio Resource Control

SC-FDMA Single Carrier Frequency Division Multiple Access

SGW Serving Gateway

SUPL Secure User Plane Location

TCP Transmission Control Protocol

UE User Entity/Equipment (Mobile Terminal)

UL Uplink

WAN Wide Area Network

WiMAX Worldwide Interoperability for Microwave Access

WLAN Wireless Local Area Network

In wireless communications networks, next generation of wirelessnetworks (e.g., fifth-generation or “5G” networks) are expected tosupport different network slices. Each network slice can be seen as anindependent network partition optimized to support the performancerequirements of a certain application category. For example, a wirelesscommunication network may contain a network slice optimized for mobilebroadband services (characterized by high data rate and medium latency),a network slice optimized for autonomous driving (characterized by lowlatency and high reliability), a network slice optimized for massiveInternet of Things (“IoT”) or Machine Type Communications (“MTC”)(characterized by low mobility and low data rate), and the like. Notethat all network slices are deployed inside the same public land mobilenetwork (“PLMN”).

Different application categories can be supported with different networkslices, each network slice being optimized to support its correspondingapplication category. One slice may be designed to support an “EnhancedMobile Broadband” application category, a second slice may be designedto support an “Ultra-reliable and Low Latency Communications”application category, and a third slice may be designed to support a“Massive Machine Type Communications” application category. A particulartype of network slice may be deployed multiple times (i.e. have multipleinstances) within the same PLMN. For example, a network operator maydeploy multiple IoT/MTC slice instances to support multiple IoTcustomers such as utility companies, automotive companies, etc.

It is expected that network slices will be created and managed vianetwork function virtualization (“NFV”) procedures. In a typicalscenario, a network operator defines different virtual networktemplates, each one specifying a collection of compute, storage, and/ornetwork resources and their configurations. Such template is essentiallya representation of a network slice. When the operator wants to create anew slice, the operator instructs the NFV platform to construct a newvirtual network based on a given template. The template may also containrules for auto-scaling the resources of a slice in order to efficientlyhandle workload variations in the time domain.

In order to support several 5G application categories, it will benecessary for the same mobile device (e.g., User Equipment (“UE”)) toconnect to multiple network slices. No existing solution enables a UE toboth select a desired network slice (based on some criteria) and toattach to the selected network slice.

BRIEF SUMMARY

Methods for selecting a network slice are disclosed. Apparatuses andsystems also perform the functions of the methods. One method, e.g., ofa remote unit, includes receiving a request to send a data packet,wherein the data packet is generated by an application of the remoteunit. The method includes identifying a network slice selectionindicator associated with the application of the remote unit andtransmitting the data packet via a network connection to a network slicein a mobile communication network, said mobile communication networksupporting a plurality of network slices, wherein the network connectionis associated with the identified network slice selection indicator.

In some embodiments, transmitting the data packet via the networkconnection to the network slice includes determining whether a networkconnection associated with the identified network slice selectionindicator exists between the remote unit and the mobile communicationnetwork, transmitting the data packet via an existing network connectionin response to determining that a network connection associated with thenetwork slice selection indicator exists between the remote unit and themobile communication network, and establishing a new network connectionwith the identified network slice selection indictor for transmittingthe data packet in response to determining that a network connectionassociated with the network slice selection indicator does not existbetween the remote unit and the mobile communication network.

In some embodiments, the method further includes receiving a selectionpolicy from the mobile communication network, the selection policy beingstored at the remote unit and comprising a plurality of rules forselecting a network slice based on the application. In such embodiments,identifying the network slice selection indicator associated with theapplication includes applying the selection policy to the application.

In some embodiments, receiving the request to send the data packetincludes receiving a network connection request that contains anapplication category parameter. In such embodiments, identifying thenetwork slice selection indicator associated with the applicationincludes verifying the application category parameter using a selectionpolicy. In certain embodiments, verifying the application categoryparameter using a selection policy comprises determining whether theapplication is permitted to use a network slice associated with theapplication category parameter. In certain embodiments, the applicationcategory parameter indicates a category selected from the groupconsisting of: a mission-critical application, an infrequent messagingapplication, and a general-purpose application.

In some embodiments, the network connection to a network slice in themobile communication network includes a connection to a network slicethat supports a traffic type associated with the application. In someembodiments, receiving the request to send the data packet includesreceiving a network connection request that contains a networkcapability parameter. In such embodiments, identifying the network sliceselection indicator associated with the application includes applying aselection policy to the network capability parameter to select thenetwork slice selection indicator.

In some embodiments, receiving the request to send the data packetincludes receiving a network connection request that contains atransport type parameter. In such embodiments, identifying the networkslice selection indicator associated with the application includesapplying a selection policy to the transport type parameter to selectthe network slice selection indicator. In certain embodiments, thetransport type parameter indicates one or more of: an access networktype, a virtual private network, a transport protocol, and a modem type.

BRIEF DESCRIPTION OF THE DRAWINGS

A more particular description of the embodiments briefly described abovewill be rendered by reference to specific embodiments that areillustrated in the appended drawings. Understanding that these drawingsdepict only some embodiments and are not therefore to be considered tobe limiting of scope, the embodiments will be described and explainedwith additional specificity and detail through the use of theaccompanying drawings, in which:

FIG. 1 is a schematic block diagram illustrating one embodiment of awireless communication system for selecting a network slice;

FIG. 2 is a schematic block diagram illustrating one embodiment of auser equipment apparatus that may be used for selecting a network slice;

FIG. 3 is a schematic block diagram illustrating one embodiment of abase station apparatus that may be used for supporting network slicing;

FIG. 4 illustrates one embodiment of a network attach procedure used forsupporting network slicing;

FIG. 5 illustrates another embodiment of a network attach procedure usedfor supporting network slicing;

FIG. 6 illustrates a further embodiment of a network attach procedureused for supporting network slicing;

FIG. 7 is a schematic block diagram illustrating one embodiment of aprotocol stack supporting network slicing; and

FIG. 8 is a schematic flow chart diagram illustrating one embodiment ofa method of a remote unit for supporting network slicing; and

FIG. 9 is a schematic flow chart diagram illustrating another embodimentof a method of a remote unit for supporting network slicing;

FIG. 10 is a schematic flow chart diagram illustrating one embodiment ofa method of a base unit for supporting network slicing; and

FIG. 11 is a schematic flow chart diagram illustrating one embodiment ofa method of a remote unit for selecting a network slice.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of theembodiments may be embodied as a system, apparatus, method, or programproduct. Accordingly, embodiments may take the form of an entirelyhardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects that may all generally bereferred to herein as a “circuit,” “module,” or “system.” Furthermore,embodiments may take the form of a program product embodied in one ormore computer-readable storage devices storing machine readable code,computer-readable code, and/or program code, referred hereafter as code.The storage devices may be tangible, non-transitory, and/ornon-transmission. The storage devices may not embody signals. In acertain embodiment, the storage devices only employ signals foraccessing code.

Certain of the functional units described in this specification may belabeled as modules, in order to more particularly emphasize theirimplementation independence. For example, a module may be implemented asa hardware circuit comprising custom very-large-scale integration(“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such aslogic chips, transistors, or other discrete components. A module mayalso be implemented in programmable hardware devices such as fieldprogrammable gate arrays, programmable array logic, programmable logicdevices, or the like.

Modules may also be implemented in code and/or software for execution byvarious types of processors. An identified module of code may, forinstance, include one or more physical or logical blocks of executablecode which may, for instance, be organized as an object, procedure, orfunction. Nevertheless, the executables of an identified module need notbe physically located together, but may include disparate instructionsstored in different locations which, when joined logically together,include the module and achieve the stated purpose for the module.

Indeed, a module of code may be a single instruction, or manyinstructions, and may even be distributed over several different codesegments, among different programs, and across several memory devices.Similarly, operational data may be identified and illustrated hereinwithin modules, and may be embodied in any suitable form and organizedwithin any suitable type of data structure. The operational data may becollected as a single data set, or may be distributed over differentlocations including over different computer-readable storage devices.Where a module or portions of a module are implemented in software, thesoftware portions are stored on one or more computer-readable storagedevices.

Any combination of one or more computer-readable medium may be utilized.The computer-readable medium may be a computer-readable storage medium.The computer-readable storage medium may be a storage device storing thecode. The storage device may be, for example, but not limited to, anelectronic, magnetic, optical, electromagnetic, infrared, holographic,micromechanical, or semiconductor system, apparatus, or device, or anysuitable combination of the foregoing.

More specific examples (a non-exhaustive list) of the storage devicewould include the following: an electrical connection having one or morewires, a portable computer diskette, a hard disk, a random access memory(“RAM”), a read-only memory (“ROM”), an erasable programmable read-onlymemory (“EPROM” or Flash memory), a portable compact disc read-onlymemory (“CD-ROM”), an optical storage device, a magnetic storage device,or any suitable combination of the foregoing. In the context of thisdocument, a computer-readable storage medium may be any tangible mediumthat can contain, or store a program for use by or in connection with aninstruction execution system, apparatus, or device.

Code for carrying out operations for embodiments may be any number oflines and may be written in any combination of one or more programminglanguages including an object oriented programming language such asPython, Ruby, Java, Smalltalk, C++, or the like, and conventionalprocedural programming languages, such as the “C” programming language,or the like, and/or machine languages such as assembly languages. Thecode may execute entirely on the user's computer, partly on the user'scomputer, as a stand-alone software package, partly on the user'scomputer and partly on a remote computer or entirely on the remotecomputer or server. In the latter scenario, the remote computer may beconnected to the user's computer through any type of network, includinga local area network (“LAN”) or a wide area network (“WAN”), or theconnection may be made to an external computer (for example, through theInternet using an Internet Service Provider (“ISP”)).

Reference throughout this specification to “one embodiment,” “anembodiment,” or similar language means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment. Thus, appearances of the phrases“in one embodiment,” “in an embodiment,” and similar language throughoutthis specification may, but do not necessarily, all refer to the sameembodiment, but mean “one or more but not all embodiments” unlessexpressly specified otherwise. The terms “including,” “comprising,”“having,” and variations thereof mean “including but not limited to,”unless expressly specified otherwise. An enumerated listing of itemsdoes not imply that any or all of the items are mutually exclusive,unless expressly specified otherwise. The terms “a,” “an,” and “the”also refer to “one or more” unless expressly specified otherwise.

Furthermore, the described features, structures, or characteristics ofthe embodiments may be combined in any suitable manner. In the followingdescription, numerous specific details are provided, such as examples ofprogramming, software modules, user selections, network transactions,database queries, database structures, hardware modules, hardwarecircuits, hardware chips, etc., to provide a thorough understanding ofembodiments. One skilled in the relevant art will recognize, however,that embodiments may be practiced without one or more of the specificdetails, or with other methods, components, materials, and so forth. Inother instances, well-known structures, materials, or operations are notshown or described in detail to avoid obscuring aspects of anembodiment.

Aspects of the embodiments are described below with reference toschematic flowchart diagrams and/or schematic block diagrams of methods,apparatuses, systems, and program products according to embodiments. Itwill be understood that each block of the schematic flowchart diagramsand/or schematic block diagrams, and combinations of blocks in theschematic flowchart diagrams and/or schematic block diagrams, can beimplemented by code. Such code may be provided to a processor of ageneral-purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions, which execute via the processor of the computer orother programmable data processing apparatus, create means forimplementing the functions/acts specified in the schematic flowchartdiagrams and/or schematic block diagrams block or blocks.

The code may also be stored in a storage device that can direct acomputer, other programmable data processing apparatus, or other devicesto function in a particular manner, such that the instructions stored inthe storage device produce an article of manufacture includinginstructions which implement the function/act specified in the schematicflowchart diagrams and/or schematic block diagrams block or blocks.

The code may also be loaded onto a computer, other programmable dataprocessing apparatus, or other devices to cause a series of operationalsteps to be performed on the computer, other programmable apparatus orother devices to produce a computer implemented process such that thecode which execute on the computer or other programmable apparatusprovide processes for implementing the functions/acts specified in theflowchart and/or block diagram block or blocks.

The schematic flowchart diagrams and/or schematic block diagrams in theFigures illustrate the architecture, functionality, and operation ofpossible implementations of apparatuses, systems, methods, and programproducts according to various embodiments. In this regard, each block inthe schematic flowchart diagrams and/or schematic block diagrams mayrepresent a module, segment, or portion of code, which includes one ormore executable instructions of the code for implementing the specifiedlogical function(s).

It should also be noted that, in some alternative implementations, thefunctions noted in the block may occur out of the order noted in theFigures. For example, two blocks shown in succession may, in fact, beexecuted substantially concurrently, or the blocks may sometimes beexecuted in the reverse order, depending upon the functionalityinvolved. Other steps and methods may be conceived that are equivalentin function, logic, or effect to one or more blocks, or portionsthereof, of the illustrated Figures.

Although various arrow types and line types may be employed in theflowchart and/or block diagrams, they are understood not to limit thescope of the corresponding embodiments. Indeed, some arrows or otherconnectors may be used to indicate only the logical flow of the depictedembodiment. For instance, an arrow may indicate a waiting or monitoringperiod of unspecified duration between enumerated steps of the depictedembodiment. It will also be noted that each block of the block diagramsand/or flowchart diagrams, and combinations of blocks in the blockdiagrams and/or flowchart diagrams, can be implemented by specialpurpose hardware-based systems that perform the specified functions oracts, or combinations of special purpose hardware and code.

The description of elements in each figure may refer to elements ofproceeding figures. Like numbers refer to like elements in all figures,including alternate embodiments of like elements.

In order to support several 5G application categories simultaneously, auser equipment (“UE”) is configured to connect to multiple networkslices simultaneously. Each network slice is optimized for a certainapplication category. In order to optimize the communication performancein this application category and potentially to reduce also the UE'sbattery consumption, the UE could steer one type of traffic to a networkslice dedicated to that application category and all other traffic toanother network slice that is optimized to support general mobilebroadband (“MBB”) traffic. For instance, a UE in a vehicle may behaveboth as an IoT gateway and as a smartphone. The UE may have anapplication that retrieves data from the vehicle's electronic system andreports them to a cloud server for analysis and diagnostics and may alsohave applications (telephony, web browsing, etc.) that enable thetypical smartphone experience. In order to optimize the communicationperformance and potentially to reduce also the UE's battery consumption,the UE could steer the IoT traffic to the IoT network slice and allother traffic to the MBB network slice that is optimized to supportsmartphone applications.

By enabling UEs to connect to different network slices that cater todifferent application categories, UE vendors are able to produce devicesthat can also be used in IoT application categories and, thus, wouldincrease the value of the devices and would bring more experiences tothe end users in a way that optimizes the network performance andreduces the UE battery consumption. Further, communication performanceand battery life may be increased by allowing the UE to selectivelyconnect to an appropriate network slice. In order to enable a UE toselectively connect to an appropriate network slice (and to connectsimultaneously with multiple network slices, as needed) the UE must beable to (a) select a desired network slice (based on some criteria) and(b) attach to the selected network slice. The present disclosurespecifies such a UE.

The concept of network slicing is similar to the concept of dedicatedcore networks (“DCN”) supported in 3GPP Rel-13 specifications. A Rel-133GPP network may support multiple core networks, each one dedicated to acertain use case. For example, a first DCN may serve smartphones andtablets, while a second and third DCN may serve smart meters that reportelectricity and water consumption, respectively. Each UE is staticallyassigned to a DCN based on subscription information. Accordingly, whenthe UE attaches to the PLMN, the serving MME, and thus the serving DCN,is selected based on subscription information retrieved from HSS.

All dedicated core networks have the same functional elements (MMES,SGWs, PGWs, etc.) and they apply the same control and user planeprocedures (e.g. the same RRC and S1 signaling procedures). In contrast,different network slices may have entirely different networkarchitectures and use different procedures. For example, the networkslice used for IoT may use much different RRC procedures from thenetwork slice used for MBB. Also, the network slice used for IoT may usea completely different radio technology from the network slice used forMBB (e.g. Narrowband IoT vs. LTE-Advanced). Thus, a key differencebetween network slicing and dedicated core networks is that differentnetwork slices can be based on different architectures and procedures,while the different dedicated core networks are all based on the samearchitecture and procedures.

FIG. 1 depicts an embodiment of a wireless communication system 100 forselecting a network slice. In one embodiment, the wireless communicationsystem 100 includes remote units 105, base units 110, and wirelesscommunication links 115. Even though a specific number of remote units105, base units 110, and wireless communication links 115 are depictedin FIG. 1, one of skill in the art will recognize that any number ofremote units 105, base units 110, and wireless communication links 115may be included in the wireless communication system 100.

The base units 110 form a radio access network (“RAN”) 120. The RAN 120is communicatively coupled to a mobile core network 140, such as a 5Gpacket core or the evolved packet core (“EPC”) specified in LTEspecifications. Note that the present disclosure is not intended to belimited to the implementation of any particular wireless communicationsystem architecture or protocol. Thus, in a non-LTE implementation, theRAN 120 may be coupled to a different type of packet core network, suchas to a “5G” packet core network. The mobile core network 140 belongs toa single public land mobile network (“PLMN”) and includes a plurality ofnetwork slices, including a first network slice 145 a, a second networkslice 145 b, and a third network slice 145 c (collectively referred toas “network slices 145”). Even though a specific number of networkslices 145 are depicted in FIG. 1, one of skill in the art willrecognize that any number of network slices 145 may be included in themobile core network 140. Each network slice 145 may be optimized for aparticular application category. For example, a first network slice 145may be optimized for mobile broadband services (high data rate, mediumlatency), a second network slice 145 b may be optimized for autonomousdriving (low latency, high reliability), and a third network slice 145 cmay be optimized for massive IoT/MTC (low mobility, low data rate). Eachoptimized service provided by a network slice 145 may correspond to anapplication category. Further, two or more of the network slices 145 maybe optimized for the same application category (e.g., the mobile corenetwork 140 may include multiple instances of a network slice 145optimized for a particular application category).

In one embodiment, the remote units 105 may include computing devices,such as desktop computers, laptop computers, personal digital assistants(“PDAs”), tablet computers, smart phones, smart televisions (e.g.,televisions connected to the Internet), set-top boxes, game consoles,security systems (including security cameras), vehicle on-boardcomputers, network devices (e.g., routers, switches, modems), or thelike. In some embodiments, the remote units 105 include wearabledevices, such as smart watches, fitness bands, optical head-mounteddisplays, or the like. Moreover, the remote units 105 may be referred toas subscriber units, mobiles, mobile stations, users, terminals, mobileterminals, fixed terminals, subscriber stations, UE, user terminals, adevice, or by other terminology used in the art. The remote units 105may communicate directly with one or more of the base units 110 viauplink (“UL”) communication signals. Furthermore, the UL communicationsignals may be carried over the wireless communication links 115.

The base units 110 may be distributed over a geographic region. Incertain embodiments, a base unit 110 may also be referred to as anaccess point, an access terminal, a base, a base station, a Node-B, aneNB, a Home Node-B, a relay node, a device, or by any other terminologyused in the art. The base units 110 are generally part of a radio accessnetwork 120 that may include one or more controllers communicablycoupled to one or more corresponding base units 110. The radio accessnetwork 120 is generally communicably coupled to one or more corenetworks (such as the mobile core network 140), which may be coupled toother networks, like the Internet and public switched telephonenetworks, among other networks. These and other elements of radio accessand core networks are not illustrated but are well known generally bythose having ordinary skill in the art. For example, one or more baseunits 110 may be communicably coupled to a mobility management entity(“MME”), a serving gateway (“SGW”), and/or a packet data network gateway(“PGW”) in the core network.

In one implementation, the wireless communication system 100 iscompliant with the long-term evolution (“LTE”) of the 3GPP protocol,wherein the base unit 110 transmits using an orthogonal frequencydivision multiplexing (“OFDM”) modulation scheme on the DL and theremote units 105 transmit on the UL using a single-carrier frequencydivision multiple access (“SC-FDMA”) scheme. More generally, however,the wireless communication system 100 may implement some other open orproprietary communication protocol, for example, WiMAX, among otherprotocols. The present disclosure is not intended to be limited to theimplementation of any particular wireless communication systemarchitecture or protocol.

The base units 110 may serve a number of remote units 105 within aserving area, for example, a cell or a cell sector via a wirelesscommunication link. The base units 110 may communicate directly with oneor more of the remote units 105 via communication signals.

The base units 110 transmit downlink (“DL”) communication signals toserve the remote units 105 in the time, frequency, and/or spatialdomain. Furthermore, the DL communication signals may be carried overthe wireless communication links 115. The wireless communication links115 may be any suitable carrier in licensed or unlicensed radiospectrum. The wireless communication links 115 may communicate with oneor more of the remote units 105 and/or one or more of the base units110.

In one embodiment, an apparatus (e.g., UE, remote unit 105) maydetermine an application category associated with a data packet andrequest a network connection to a network slice 145 corresponding to theidentified application category. In such an embodiment, a categoryselection policy may be used to identify which application category isassociated with the data packet. The category selection policy mayinclude one or more rules for selecting the application category basedon characteristics of the data packet. The apparatus may thencommunicate the data packet and any subsequent data packets of the sameapplication category over a network slice 145 optimized for theapplication category. Further, the apparatus may receive one or morereturn data packets over the same network slice 145, the return packetsbeing responses to the transmitted data packets. Accordingly, byselecting and communicating over a network slice 145 optimized for anapplication category associated with the data packet(s), the apparatusoptimizes the communication performance in this application category andpotentially reduce the UE's battery consumption.

In certain embodiments, an application of a remote unit 105 generates adata packet that is to be transmitted via a mobile communication network(e.g., the RAN 120 and mobile core network 140), where the mobilecommunication network supports a plurality of network slices 145. Here,the remote unit 105 identifies a network slice selection indicatorassociated with the data packet and transmits the data packet using anetwork connection to a network slice in the mobile communicationnetwork, where the network connection is associated with the identifiednetwork slice selection indicator.

In one embodiment, the remote unit 105 determines whether a networkconnection associated with the identified network slice selectionindicator already exists between the remote unit 105 and the mobilecommunication network (e.g., the mobile core network 140) andestablishes a new network connection with the indicated network slice inresponse to a network connection associated with the network sliceselection indicator not existing between the remote unit 105 and themobile communication network. Here, transmitting the data packetincludes the remote unit 105 transmitting via the new networkconnection.

FIG. 2 depicts one embodiment of a user equipment apparatus 200 that maybe used for selecting a network slice. In various embodiments, the userequipment apparatus 200 may be one embodiment of the remote unit 105. Asdepicted, the user equipment apparatus 200 may include a processor 205,a memory 210, an input device 215, an output device 220, and atransceiver 225. In some embodiments, the input device 215 and theoutput device 220 are combined into a single device, such as atouchscreen. In certain embodiments, the user equipment apparatus 200may not include any input device 215 and/or output device 220. Invarious embodiments, the user equipment apparatus 200 may include one ormore of the processor 205, the memory 210, and the transceiver 225, andmay not include the input device 215 and/or the output device 220.

The processor 205, in one embodiment, may include any known controllercapable of executing computer-readable instructions and/or capable ofperforming logical operations. For example, the processor 205 may be amicrocontroller, a microprocessor, a central processing unit (“CPU”), agraphics processing unit (“GPU”), an auxiliary processing unit, a fieldprogrammable gate array (“FPGA”), or similar programmable controller. Insome embodiments, the processor 205 executes instructions stored in thememory 210 to perform the methods and routines described herein. Theprocessor 205 is communicatively coupled to the memory 210, the inputdevice 215, the output device 220, and the transceiver 225. In certainembodiments, the processor 205 may identify an application categoryassociated with a received data packet (e.g., received from anapplication executing on the processor 205) and control the transceiver225 to request a network connection corresponding to the identifiedapplication category.

In various embodiments, the processor 205 receives a request to send adata packet, wherein the data packet is generated by an application ofthe user equipment apparatus 200. The processor 205 may identify anetwork slice selection indicator associated with the application of theapparatus and control the transceiver 225 to transmit the data packetvia a network connection to a network slice in the mobile communicationnetwork, wherein the network connection is associated with theidentified network slice selection indicator.

In certain embodiments, transmitting the data packet via the networkconnection to the network slice includes the processor 205 determiningwhether a network connection associated with the identified networkslice selection indicator exists between the remote unit and the mobilecommunication network. In response to the processor 205 determining thata network connection associated with the network slice selectionindicator exists between the remote unit and the mobile communicationnetwork, the transceiver 225 transmits the data packet via an existingnetwork connection. In response to determining that a network connectionassociated with the network slice selection indicator does not existbetween the remote unit and the mobile communication network, theprocessor 205 establishes a new network connection with the identifiednetwork slice selection indictor for transmitting the data packet.Thereafter, the transceiver 225 uses this new network transmission totransmit the data packet.

In certain embodiments, the processor 205 further receives a selectionpolicy from the mobile communication network, the selection policy beingstored at the apparatus and comprising a plurality of rules forselecting a network slice based on the application. In such embodiments,identifying the network slice selection indicator associated with theapplication includes the processor 205 applying the selection policy tothe application.

In certain embodiments, receiving the request to send the data packetincludes the processor 205 receiving a network connection request thatcontains an application category parameter. In such embodiments,identifying the network slice selection indicator associated with theapplication includes the processor 205 verifying the applicationcategory parameter using a selection policy. In certain embodiments,verifying the application category parameter includes the processor 205determining whether the application is permitted to use a network sliceassociated with the application category parameter. In certainembodiments, the application category parameter indicates a categoryselected from the group consisting of: a mission-critical application,an infrequent messaging application, and a general-purpose application.

In some embodiments, the network connection to a network slice in themobile communication network includes a connection to a network slicethat supports a traffic type associated with the application. In certainembodiments, receiving the request to send the data packet includes theprocessor 205 receiving a network connection request that contains anetwork capability parameter. In such embodiments, the processor 205identifies the network slice selection indicator associated with theapplication by applying a selection policy to the network capabilityparameter to select the network slice selection indicator.

In certain embodiments, receiving the request to send the data packetincludes the processor 205 receiving a network connection request thatcontains a transport type parameter. In such embodiments, the processor205 identifies the network slice selection indicator associated with theapplication by applying a selection policy to the transport typeparameter to select the network slice selection indicator. Here, thetransport type parameter may indicate one or more of: an access networktype, a virtual private network, a transport protocol, and a modem type.

The memory 210, in one embodiment, is a computer-readable storagemedium. In some embodiments, the memory 210 includes volatile computerstorage media. For example, the memory 210 may include a RAM, includingdynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or staticRAM (“SRAM”). In some embodiments, the memory 210 includes non-volatilecomputer storage media. For example, the memory 210 may include a harddisk drive, a flash memory, or any other suitable non-volatile computerstorage device. In some embodiments, the memory 210 includes bothvolatile and non-volatile computer storage media. In some embodiments,the memory 210 stores data relating to a category selection policy. Insome embodiments, the memory 210 also stores program code and relateddata, such as an operating system or other controller algorithmsoperating on the user equipment apparatus 200.

The input device 215, in one embodiment, may include any known computerinput device including a touch panel, a button, a keyboard, a stylus, amicrophone, or the like. In some embodiments, the input device 215 maybe integrated with the output device 220, for example, as a touchscreenor similar touch-sensitive display. In some embodiments, the inputdevice 215 includes a touchscreen such that text may be input using avirtual keyboard displayed on the touchscreen and/or by handwriting onthe touchscreen. In some embodiments, the input device 215 includes twoor more different devices, such as a keyboard and a touch panel.

The output device 220, in one embodiment, may include any knownelectronically controllable display or display device. The output device220 may be designed to output visual, audible, and/or haptic signals. Insome embodiments, the output device 220 includes an electronic displaycapable of outputting visual data to a user. For example, the outputdevice 220 may include, but is not limited to, an LCD display, an LEDdisplay, an OLED display, a projector, or similar display device capableof outputting images, text, or the like to a user. As another,non-limiting, example, the output device 220 may include a wearabledisplay such as a smart watch, smart glasses, a heads-up display, or thelike. Further, the output device 220 may be a component of a smartphone, a personal digital assistant, a television, a table computer, anotebook (laptop) computer, a personal computer, a vehicle dashboard, orthe like.

In certain embodiments, the output device 220 includes one or morespeakers for producing sound. For example, the output device 220 mayproduce an audible alert or notification (e.g., a beep or chime). Insome embodiments, the output device 220 includes one or more hapticdevices for producing vibrations, motion, or other haptic feedback. Insome embodiments, all or portions of the output device 220 may beintegrated with the input device 215. For example, the input device 215and output device 220 may form a touchscreen or similar touch-sensitivedisplay. In other embodiments, the output device 220 may be located nearthe input device 215.

The transceiver 225 communicates with the mobile communication networksupporting a plurality of application categories via a plurality ofnetwork slices, each network slice associated with a particularapplication category. In one embodiment, the transceiver 225 is used torequest a network connection corresponding to an identified applicationcategory and otherwise communicate with the base unit 110. For example,the transmitter 230 may request a network connection associated with anapplication category by transmitting a radio resource control (“RRC”)connection setup message, such as an RRC Connection Setup Completemessage, containing an application category parameter corresponding tothe identified application category.

The transceiver 225 includes at least transmitter 230 and at least onereceiver 235. One or more transmitters 230 may be used to provide ULcommunication signals to a base unit 110, such as the UL transmissionsdescribed herein. Similarly, one or more receivers 235 may be used toreceive DL communication signals from the base unit 110, as describedherein. Although only one transmitter 230 and one receiver 235 areillustrated, the user equipment apparatus 200 may have any suitablenumber of transmitters 230 and receivers 235. Further, thetransmitter(s) 230 and the receiver(s) 235 may be any suitable type oftransmitters and receivers. In one embodiment, the transceiver 225includes a first transmitter/receiver pair used to communicate with amobile communication network over licensed radio spectrum and a secondtransmitter/receiver pair used to communicate with a mobilecommunication network over unlicensed radio spectrum.

In certain embodiments, the first transmitter/receiver pair used tocommunicate with a mobile communication network over licensed radiospectrum and the second transmitter/receiver pair used to communicatewith a mobile communication network over unlicensed radio spectrum maybe combined into a single transceiver unit, for example a single chipperforming functions for use with both licensed and unlicensed radiospectrum. In some embodiments, the first transmitter/receiver pair andthe second transmitter/receiver pair may share one or more hardwarecomponents. For example, certain transceivers 225, transmitters 230, andreceivers 235 may be implemented as physically separate components thataccess a shared hardware resource and/or software resource, such as forexample, a radio network interface.

In various embodiments, one or more transmitters 230 and/or one or morereceivers 235 may be implemented and/or integrated into a singlehardware component, such as a multi-transceiver chip, asystem-on-a-chip, an ASIC, or other type of hardware component. Incertain embodiments, one or more transmitters 230 and/or one or morereceivers 235 may be implemented and/or integrated into a multi-chipmodule. In some embodiments, other components such as the radio networkinterface or other hardware components/circuits may be integrated withany number of transmitters 230 and/or receivers 235 into a single chip.In such embodiment, the transmitters 230 and receivers 235 may belogically configured as a transceiver 225 that uses one more commoncontrol signals or as modular transmitters 230 and receivers 235implemented in the same hardware chip or in a multi-chip module.

FIG. 3 depicts another embodiment of a base station apparatus 300 thatmay be used for supporting network slicing. The base station apparatus300 includes one embodiment of the base unit 110. Furthermore, the baseunit 110 may include a processor 305, a memory 310, an input device 315,an output device 320, a radio transceiver 325, and a network interface330. As may be appreciated, the processor 305, the memory 310, the inputdevice 315, and the output device 320 may be substantially similar tothe processor 205, the memory 210, the input device 215, and the outputdevice 220 of the user equipment apparatus 200, respectively. In certainembodiments, the processor 305 may be used to determine whether the baseunit 110 will apply traffic steering rules for routing data traffic on afirst route across a first access network and a second route across asecond access network.

In some embodiments, the processor 305 controls the radio transceiver325 to transmit DL signals to a remote unit 105. The processor 305 mayalso control the radio transceiver 325 to receive UL signals from theremote unit 105. For example, the processor 305 may control the radiotransceiver 325 to receive a RRC Connection Request and transmit an RRCConnection Setup message. The processor 305 may further identify anapplication category parameter included in a received RRC ConnectionSetup Complete message and select a network slice 145 based on theapplication category parameter. The processor 305 may then establish aconnection between the remote unit 105 and the selected network slice145, for example via the radio transceiver 325 and the network interface330.

In various embodiments, the processor 305 receives, via the radiotransceiver 325, a request to establish a network connection with themobile communication network and identifies a network slice selectionindicator associated with the request. In one embodiment, the request isa radio resource control (“RRC”) message containing the network sliceselection indicator. For example, the RRC message may be an RRCconnection setup message (e.g., transmitted during an RRC connectionsetup procedure). In other embodiments, the RRC message may be anon-setup message.

In some embodiments, the processor 305 selects a management function ina network slice 145 that supports the network slice selection indicatorand establishes, via the network interface 330, the requested connectionby using the selected management function in the network slice 145. Incertain embodiments, selecting the management function in a networkslice based on the network slice selection indicator includes theprocessor 305 identifying a network slice that supports an applicationcategory indicated in the network slice selection indicator. In oneembodiment, the application category is selected from the groupconsisting of: a mission-critical application, an infrequent messagingapplication, and a general-purpose application.

In certain embodiments, the processor 305 establishes, e.g., via thenetwork interface 330, a signaling connection with a management functionin each network slice 145 in the mobile communication network. Here, theprocessor 305 also identifies a traffic type associated with eachmanagement function. In such embodiments, selecting the managementfunction in a network slice 145 based on the network slice selectionindicator includes the processor 305 matching the network sliceselection indicator to a network slice 145 using the traffic typeassociated with the management function in a network slice 145.

In some embodiments, establishing the requested connection by using theselected management function in the selected network slice includes theprocessor 305 sending an initial user equipment (“UE”) message to theselected management function and receiving a downlink non-access stratum(“NAS”) transport message from the selected management function.

The radio transceiver 325, in one embodiment, is configured tocommunicate wirelessly with the remote unit 105. In certain embodiments,the radio transceiver 325 comprises a transmitter used to transmit DLcommunication signals to the remote unit 105 and a receiver used toreceive UL communication signals from the remote unit 105. For example,the receiver may receive a RRC Connection Request and the transmittermay transmit an RRC Connection Setup message.

The radio transceiver 325 may communicate simultaneously with aplurality of remote unit 105. For example, the transmitter may transmitDL communication signals received by multiple remote units 105. Asanother example, the receiver may simultaneously receive ULcommunication signals from multiple remote units 105. The radiotransceiver 325 may include any suitable number and any suitable typesof transmitters and receivers. Upon selection of a network slice 145based on a received application category parameter, the base unit 110may bridge the remote unit 105 to the selected network slice 145 via theradio transceiver 325 and the network interface 330

The radio transceiver 325 includes at least one transmitter and at leastone receiver. One or more transmitters may be used to provide DLcommunication signals to the remote units 105, such as the DLtransmissions described herein. Similarly, one or more receivers may beused to receive UL communication signals from the remote units 105, asdescribed herein. Moreover, the base station apparatus 300 may have anysuitable number of transmitters and receivers. Further, thetransmitter(s) and the receiver(s) may be any suitable type oftransmitters and receivers. In one embodiment, the radio transceiver 325includes a first transmitter/receiver pair used to communicate with amobile communication network over licensed radio spectrum and a secondtransmitter/receiver pair used to communicate with a mobilecommunication network over unlicensed radio spectrum.

In certain embodiments, the first transmitter/receiver pair used tocommunicate with a mobile communication network over licensed radiospectrum and the second transmitter/receiver pair used to communicatewith a mobile communication network over unlicensed radio spectrum maybe combined into a single transceiver unit, for example a single chipperforming functions for use with both licensed and unlicensed radiospectrum. In some embodiments, the first transmitter/receiver pair andthe second transmitter/receiver pair may share one or more hardwarecomponents. For example, certain transceivers, transmitters, andreceivers may be implemented as physically separate components thataccess a shared hardware resource and/or software resource, such as forexample, a radio network interface.

In various embodiments, one or more transmitters and/or one or morereceivers may be implemented and/or integrated into a single hardwarecomponent, such as a multi-transceiver chip, a system-on-a-chip, anASIC, or other type of hardware component. In certain embodiments, oneor more transmitters and/or one or more receivers may be implementedand/or integrated into a multi-chip module. In some embodiments, othercomponents such as the radio network interface or other hardwarecomponents/circuits may be integrated with any number of transmittersand/or receivers into a single chip. In such embodiment, thetransmitters and receivers may be logically configured as a transceiverthat uses one more common control signals or as modular transmitters andreceivers implemented in the same hardware chip or in a multi-chipmodule.

The network interface 330, in one embodiment, is configured tocommunicate with one or more network functions in the mobile corenetwork 140. In one embodiment, the network interface 330 establishesnetwork connections with one or more network slices 145 within themobile core network 140. For example, the processor 305 may control thenetwork interface 330 to establish a network connection with one or moreMMEs within a network slice 145 using S1 setup request and S1 setupresponse messages. Upon selection of a network slice 145 based on areceived application category parameter the network interface 330 maybridge the remote unit 105 to the selected network slice 145 using knownsignaling messages between the remote unit 105, the base unit 110, andthe mobile core network 140.

FIG. 4 illustrates one embodiment of a network attach procedure 400 usedfor supporting network slicing. In the illustrated embodiment,communication with a UE 402 and an eNode B (“eNB”) 416 are illustrated.In certain embodiments, the UE 402 may be one embodiment of the remoteunit 105. In some embodiments, the eNB 416 may be one embodiment of thebase unit 110. Moreover, communication between an application 404running on the UE 402 and an operating system (“OS”) 406 running on theUE 402 are illustrated. The OS 406 may include a connectivity manager408 and a cellular modem 410. The cellular modem 410 may include anon-access stratum (“NAS”) layer 412 and a radio resource control(“RRC”) layer 414 as part of the access stratum layer.

As illustrated, the application 404 may request the OS 406 to establisha network connection with certain characteristics. To do so, theapplication 404 may send a “Request Network Connection” message 420 tothe connectivity manager 408 of the OS 406. In one embodiment, the OS406 is an ANDROID™ operating system and the “Request Network Connection”message 420 corresponds to a “requestNetwork( )” API call. The “RequestNetwork Connection” message 420 indicates the type of service(s) thatshould be accessible via the connection.

The “Request Network Connection” message 420 includes an applicationcategory parameter 421 which indicates how the requested networkconnection will be used by the application 404. For example, theapplication category parameter 421 may indicate“ApplicationCategory=General-Purpose” if the connection is going to beused for accessing general-type of services, such as web browsing,email, video/audio streaming, or the like. In another example, theapplication category parameter 421 may indicate“ApplicationCategory=Mission-Critical” if the connection is going to beused for low-latency, mission-critical communications such aspublic-safety communication, self-automated driving, or the like. In yetanother example, the application category parameter 421 may indicate“ApplicationCategory=Infrequent Messaging” if the connection is going tobe used for infrequently sending of data, such as relaying sensor datato a cloud server.

The application category parameter 421 helps the OS 406 and/or the eNB416 select an appropriate network slice for supporting the requestedconnection. For example, if the application indicates“ApplicationCategory=Infrequent Messaging”, then the eNB 416 mayestablish the requested connection via the network slice that isoptimized to support IoT or MTC traffic. In certain embodiments, theapplication category parameter 421 may be associated with theapplication 404, so that all network communication by the application404 is associated with a single application category. In otherembodiments, the application 404 may have network communications in morethan one application category. The specific values of the applicationcategory parameter 421 given above are exemplary, and non-limiting. Insome embodiments, the format and acceptable values of the applicationcategory parameter 421 may be defined by a network operator and/or by anetwork standards body (e.g., the 3GPP or other telecommunicationsassociation).

In some embodiments, the “Request Network Connection” message 420 alsoincludes a “network capabilities” parameter indicating a requestednetwork service type. For example, the “network capabilities” parametermay request IP Multimedia Subsystem (“IMS”) services, multimediamessaging service (“MMS”) services, Internet services, richcommunication services (“RCS”) services, secure user plane location(“SUPL”) services, or the like. In some embodiments, the “RequestNetwork Connection” message 420 also includes a “transport type”parameter indicating a requested type of transport. For example, the“transport type” parameter may request transport via cellularconnection, WLAN connection (e.g., a WIFI® or BLUETOOTH® connection),Ethernet connection, virtual private network (“VPN”), or the like.

The connectivity manager 408 receives the “Request Network Connection”message 420 and determines whether the application 404 is permitted toutilize the requested application category parameter 421. In someembodiments, the user must give permission for the application 404 toutilize a particular application category. For example, the user maygive permission for the application 404 to utilize one or moreapplication categories during installation of the application 404. Asanother example, the user may dynamically indicate permission to utilizea particular application category, such as in response to a prompt fromthe OS 406.

In other embodiments, a network operator must give permission for theapplication 404 to utilize a particular application category. Forexample, the network operator may permit a game application to utilize a“General-Purpose” application category, but refuse permission for thegame application to utilize a “Mission-Critical” application category.In one embodiment, the network operator may provision the UE 402 with alist of applications permitted to utilize an application categorysupported in the operator's network. The list of applications may be awhitelist (e.g., only applications on the whitelist are approved toutilize an application category), a blacklist (e.g., applications on theblacklist are denied from utilizing an application category), or othersuitable list.

The connectivity manager 408 also determines whether the UE 402 hasalready established a network connection that supports the receivedapplication category parameter 421. For example, the connectivitymanager 408 may maintain a list of established (active) networkconnections and an application category supported by the networkconnection (or, alternatively, a network slice 145 associated with theconnection). In response to a network connection already beingestablished that supports the received application category parameter421, then the OS will transfer data for the application 404 using theestablished network connection. Otherwise, the connectivity manager 408sends a request to establish a data connection. Here it is presumed thatthe connection will be established via cellular modem (e.g., the“Request Network Connection” message 420 may include a transport typeparameter specifying cellular connection and/or the OS 406 may selectthe cellular modem as the best, or only, available modem). Accordingly,the connectivity manager 408 sends an “Establish Data Connection”message 422 to the cellular modem 410, specifically to the NAS layer412. Similar procedures may be used with other modems (e.g., WIFI®).

The “Establish Data Connection” message 422 includes the applicationcategory parameter 421. In some embodiments, the “Establish DataConnection” message 422 also includes an Access Point Name (“APN”)parameter indicating a specific APN with which the cellular modem 410should establish a connection. The APN may be selected based on a typeof service requested. For example, the APN may be selected based on avalue of a network capabilities parameter included in the “RequestNetwork Connection” message 420.

The NAS layer 412 receives the “Establish Data Connection” message 422and creates an initial NAS message. Then, the NAS layer 412 forwards theNAS message to the RRC layer 414. For example, according to 3GPP LTEprocedures, the NAS layer 412 may create and forward a “NAS AttachRequest” message 424. In another example, may create and forward a “NASPDN Connectivity Request” message. When using other communicationstandard procedures, the NAS layer 412 may create an equivalent attachrequest message.

The “NAS Attach Request” message 424 includes the application categoryparameter 421. In some embodiments, the “NAS Attach Request” message 424also includes a PLMN identity (“PLMN-ID”) parameter, selected accordingto established procedures. The PLMN identity is used by the radio accessnetwork in case the radio access network is shared by several PLMNs inorder to direct the UE's traffic to one of these PLMNs.

The RRC layer 414 receives the “NAS Attach Request” message 424 anddetermines a radio signaling procedure based on the application categoryparameter 421. For example, when the application category parameter 421has a specific value, the RRC layer may determine that no RRC connectionis required. However, for other application category parameter 421values, the RRC layer may trigger an RRC connection 426, for example, bysending an RRC Connection Request message to the eNB 416 and receivingan RRC Connection Setup message in return.

In all cases, the RRC layer 414 sends an RRC message to the eNB 416based on the received “NAS Attach Request” message 424. As depicted,this message may be an RRC connection setup message 428, such as an “RRCConnection Setup Complete” message (according to the existing 3GPP LTEstandards), but any other message defined in a radio protocol can beused.

The RRC connection setup message 428 includes the application categoryparameter 421. In one embodiment, the RRC layer 414 may send an “RRCConnection Setup Complete” message 428 in response to receiving an RRCConnection Setup message. However, in other embodiments, the RRC layer414 may send a non-setup RRC message to the eNB 416, the non-setup RRCmessage including the application category parameter 421, for example inresponse to the RRC layer 414 determining that no RRC connection isrequired. In some embodiments, the “RRC Connection Setup Complete”message 428 may also include other parameters from the initial NASMessage (e.g., the “NAS Attach Request” message 424), such as theselected PLMN-ID.

Upon receiving the RRC message 428, the eNB 416 selects 430 a networkslice 145 with which to create the requested network connection based onthe application category parameter 421. In some embodiments, selecting430 the network slice 145 includes the eNB 416 identifying a networkslice that supports (e.g., is optimized to support) an applicationcategory indicated in the application category parameter 421 andselecting an MME of the identified network slice 145. The eNB 416 mayfurther establish a network connection between the UE 402 and thenetwork slice 145 (e.g., the MME), as described below with reference toFIG. 6.

In some embodiments, a second application (not shown) running on the UE402 may request a network connection using a different applicationcategory parameter 421. In such embodiments, the UE 402 will request asecond network connection, the second network connection being to asecond network slice 145 b that supports (e.g., is optimized to support)the application category indicated in the different application categoryparameter 421. Accordingly, the UE 402 may end up being attached to twodifferent network slices 145 and having two different IP connections, asdepicted in FIG. 7.

The network attach procedure 400 assumes that the application 404 iscapable of explicitly requesting a network connection for a certainapplication category (e.g., due to the inclusion of the applicationcategory parameter 421 in the “Request Network Connection” message 420).However, legacy applications may be incapable of explicitly requesting anetwork connection for a certain application category, but instead maysend a request that does not include an application category parameter421. Additionally, some applications may simply request to send datapackets without prior requesting a network connection with specificcharacteristics. Network attach procedures where an application categoryparameter 421 is not sent by an application are addressed below withreference to FIG. 5.

FIG. 5 illustrates another embodiment of a network attach procedure 500used for supporting network slicing. The network attach procedure 500represents an alternative to the network attach procedure 400. While thenetwork attach procedure 500 is directed primarily to embodiments wherean application does not explicitly requesting a network connection for acertain application category, in some embodiments the network attachprocedure 500 may be used to even when an application explicitlyrequests a network connection for a certain application category.

In the illustrated embodiment, communication with a UE 402 and an eNodeB (“eNB”) 416 are illustrated. Moreover, communication between anapplication 404 running on the UE 402 and an operating system (“OS”) 406running on the UE 402 are illustrated. The OS 406 may include anetworking layer 502, a category selection policy 504, and a cellularmodem 410. The cellular modem 410 may include a non-access stratum(“NAS”) layer 412 and a radio resource control (“RRC”) layer 414 as partof the access stratum. In certain embodiments, the UE 402, the cellularmodem 410, and the eNB 416 may substantially similar to those describedabove with reference to FIG. 4.

As illustrated, the application 404 may request 506 to send a datapacket to the network. In one embodiment, the application 404 requeststo send the data packet without prior requesting a network connection toestablish a network connection with certain characteristics. In anotherembodiment, the application 404 may send a network connection requestthat lacks an indication of an application category. In such anembodiment, the network connection may include a “network capabilities”parameter indicating a requested network service type and/or a“transport type” parameter indicating a requested type of transport. The“network capabilities” parameter and the “transport type” parameter aredescribed above, with reference to FIG. 4.

The OS, upon receiving the request 506 to send a data packet, routes therequest to the networking layer 502. The networking layer 502 consults508 the category selection policy 504 to determine an applicationcategory for the request 506. The category selection policy 504 containsrules for associating a data packet with a particular applicationcategory parameter 421. The category selection policy 504 may determinethe application category parameter 421 based on an identity of theapplication 404, an application type of the application 404 (e.g., game,utility, productivity, navigation, music, etc.), a recipient address oraddress range (e.g., IP address, domain name, etc.), a transportprotocol (e.g., transmission control protocol (“TCP”), user datagramprotocol (“UDP”), etc.), a recipient port number (e.g. HTTP port 80), orcombinations thereof. In some embodiments, the rules of the categoryselection policy 504 are arranged into a hierarchy such that rules of ahigher rank may override rules of a lower rank.

For example, the category selection policy 504 may include rules thatdata packets from a particular application “Application-x” are to beassociated with “ApplicationCategory=Mission-Critical,” while datapackets from another application “Application-y” are to be associatedwith “ApplicationCategory=Infrequent Messaging.” As another example, thecategory selection policy 504 may include a rule that data packetsaddressed to the domain “example.IoT.com” should be associated with“ApplicationCategory=Infrequent Messaging.” As a further example, thecategory selection policy 504 may include a rule that UDP data packetsare to be associated with “ApplicationCategory=General-Purpose.” In yetanother example, the category selection policy 504 may include a rulethat TCP data packets destined to 143.128.1.0/24 (as an example of an IPaddress range) should be associated with“ApplicationCategory=Mission-Critical.” The category selection policy504 may also include a catch-all rule that any data packet notexplicitly associated with “ApplicationCategory=Mission-Critica/” or“ApplicationCategory=Infrequent Messaging” are to be associated with“ApplicationCategory=General-Purpose.”

The category selection policy 504 may be statically pre-configured inthe UE or may be provisioned and managed over-the-air by a networkmanagement entity, for example by the Access Network Discovery &Selection Function (“ANDSF”) specified in the 3GPP specifications. Wherethe UE 402 operates using other standards, the category selection policy504 may be provisioned by an equivalent network management entity. Inone embodiment, the category selection policy 504 is created by anetwork operator and is provisioned in the UE 402 for steering UEtraffic to the various network slices 145 in the mobile core network 140or other packet core (e.g. the “5G packet core”). As an example, amobile network operator may provision a category selection policy 504 inthe UE 402 that steers all traffic of a certain application in the UE toa network slice 145 optimized to support IoT services.

In some embodiments, the networking layer 502 may verify an applicationcategory parameter 421 where the request 506 to send a data packet is anetwork connection request that includes an application categoryparameter 421. For example, the category selection policy 504 mayinclude one or more rules based on the identity or application type ofthe application 404 that override any application category parameter 421included in a network connection request from the application 404. Inother embodiments, the networking layer 502 may override a rule in thecategory selection policy 504 in response to the request 506 being anetwork connection request that includes an application categoryparameter 421. For example, the category selection policy 504 mayinclude one or more rules based on the recipient address, data packettype, or transport protocol type that are overridden by an applicationcategory parameter 421 included in a network connection request from theapplication 404.

Having determined the application category parameter 421 for thereceived data packet, the networking layer 502 may also determinewhether the UE 402 has already established a network connection thatsupports the received application category parameter 421. For example,the networking layer 502 may maintain a list of established (active)network connections and an application category supported by the networkconnection (or, alternatively, a network slice 145 associated with theconnection). In response to a network connection already beingestablished that supports the received application category parameter421, then the OS will transfer data for the application 404 using theestablished network connection. Otherwise, the networking layer 502sends a request to establish a data connection. Here it is presumed thatthe connection will be established via cellular modem (e.g., the“Request Network Connection” message 420 may include a transport typeparameter specifying cellular connection and/or the OS 406 may selectthe cellular modem as the best, or only, available modem). Accordingly,the networking layer 502 sends an “Establish Data Connection” message422 to the cellular modem 410, specifically to the NAS layer 412.Similar procedures may be used with other modems (e.g., WIFI®).

As discussed above, the “Establish Data Connection” message 422 includesthe application category parameter 421 and optionally includes an AccessPoint Name (“APN”) parameter. The NAS layer 412 receives the “EstablishData Connection” message 422 and creates an initial NAS message. Then,the NAS layer 412 forwards the NAS message to the RRC layer 414. Forexample, according to 3GPP LTE procedures, the NAS layer 412 may createand forward a “NAS Attach Request” message 424. In another example, maycreate and forward a “NAS PDN Connectivity Request” message. When usingother communication standard procedures, the NAS layer 412 would createan equivalent attach request message.

As discussed above, the “NAS Attach Request” message 424 includes theapplication category parameter 421, and optionally includes a PLMNidentity (“PLMN-ID”) parameter. The RRC layer 414 receives the “NASAttach Request” message 424 and determines a radio signaling procedurebased on the application category parameter 421. For example, when theapplication category parameter 421 has a specific value, the RRC layer414 may determine that no RRC connection is required. However, for otherapplication category parameter 421 values, the RRC layer may trigger anRRC connection 426, for example, by sending an RRC Connection Requestmessage to the eNB 416 and receiving an RRC Connection Setup message inreturn.

As before, the RRC layer 414 sends an RRC message to the eNB 416 basedon the received “NAS Attach Request” message 424. In the depictedembodiment, the RRC layer 414 sends an RRC connection setup message 428that includes the application category parameter 421. For example, theRRC layer 414 may send an “RRC Connection Setup Complete” message inresponse to receiving an RRC Connection Setup message. However, in otherembodiments, the RRC layer 414 may send a non-setup RRC message to theeNB 416, the non-setup RRC message including the application categoryparameter 421, for example in response to the RRC layer 414 determiningthat no RRC connection is required. Upon receiving the RRC message 428,the eNB 416 selects 430 a network slice 145 with which to create therequested network connection based on the application category parameter421. In some embodiments, selecting 430 the network slice 145 includesthe eNB 416 identifying a network slice that supports (e.g., isoptimized to support) an application category indicated in theapplication category parameter 421 and selecting an MME of theidentified network slice 145. The eNB 416 may further establish anetwork connection between the UE 402 and the network slice 145 (e.g.,the MME), as described below with reference to FIG. 6.

In some embodiments, a second application (not shown) running on the UE402 may also request to send a data packet and the category selectionpolicy 504 may determine a different application category parameter 421from the application 404. In such embodiments, the UE 402 will request asecond network connection, the second network connection being to asecond network slice 145 b that supports (e.g., is optimized to support)the application category indicated in the different application categoryparameter 421. Accordingly, the UE 402 may end up being attached to twodifferent network slices 145 and having two different IP connections, asdiscussed below with reference to FIG. 7.

FIG. 6 illustrates a further embodiment of a network attach procedure600 used for supporting network slicing. In the illustrated embodiment,communication between a UE 402 and an eNB 416 are illustrated. Moreover,communication between the eNB 416 and the packet core in a PLMN 602 isillustrated. The UE 402 and the eNB 416 may be embodiments of a remoteunit 105 and base unit 110, respectively, and may be substantiallysimilar to the UE 402 and eNB 416 discussed above with reference toFIGS. 4 and 5.

The PLMN 602 includes a first network slice (“Slice A”) 604 and a secondnetwork slice (“Slice B”) 606. Each network slice 604, 606 may includeat least two MMEs (e.g., Slice A 604 may include at least a MME-x andMME-y, while Slice B 606 may include at least a MME-a and MME-b).Furthermore, the MMEs of the network slices may include features similarto those found in the base unit 110 (e.g., the MMEs may include aprocessor 305, a memory 310, an input device 315, a output device 320, aradio transceiver 325, and/or a network interface 330).

The network attach procedure 600 shows how the eNB 416 (or equivalentbase station) selects an MME (or equivalent management entity) in anetwork slice based on the application category parameter 421 requestedby the UE 402. As illustrated, the eNB 416 establishes S1 signalingconnections with multiple MMEs according to the existing 3GPPspecifications. In some embodiments, these connections are establishedwhen the eNB 416 is first initialized and brought into service.

Establishing S1 signaling connections includes exchanging 608 S1 SetupRequest and Setup Response messages between the eNB and each MME. TheeNB 416 sends conventional S1 Setup Request messages (1 a.) and receivesS1 Setup Response messages (1 b.) from each MME which include a servedcategory parameter 609. The served category parameter 609 indicates anapplication category supported by the specific MME. Through the exchange608 of S1 Setup messages, the eNB 416 identifies an application categorysupported by every connected MME.

For example, in MME-x and MME-y (which are part of Slice A 604) mayindicate Served ApplicationCategory=Mission-Critical. This servedcategory parameter 609 indicates that MME-x and MME-y are part of anetwork slice (e.g., Slice A 604) that is optimized to supportlow-latency, high-reliability (e.g., Mission-Critical) communications.Similarly, MME-a and MME-b (which are part of Slice B 606) may indicateServed ApplicationCategory=General-Purpose, to indicate that these MMEsare part of a network slice (e.g., Slice B 606) that supports mobilebroadband services.

At some point in time, the UE 402 receives 610 a data packet (e.g., froman application 404 running on the UE) and identifies an applicationcategory associated with the data packet. In some embodiments, the datapacket is a network connection request, such as the “Request NetworkConnection” message 420 discussed above which contains an applicationcategory parameter 421. In such embodiments, identifying the applicationcategory includes parsing the network connection request to identify theapplication category parameter 421. In other embodiments, the datapacket is a network connection request without an application categoryparameter 421 or simply a request to send data packets without priorrequesting a network connection. In such embodiments, the UE 402 maydetermine an application category parameter 421 based on a categoryselection policy 504. Here it is assumed that the UE 402 does notalready have an established network connection to a network slicecorresponding to the application category.

The UE 402 may optionally exchange 612 RRC connection request/setupmessages with the eNB 416, as discussed above with reference to FIGS. 4and 5. For example, an RRC layer 414 may trigger the exchange 612 of RRCconnection messages. Regardless of whether RRC connection request/setupmessages 612 are exchanged, the UE 402 transmits an RRC connection setupcomplete message 614 to the eNB 416 which includes an applicationcategory parameter 421 indicating the application category identifiedfor the data packet.

The eNB 416 selects 616 a MME associated with the indicated applicationcategory. In some embodiments, the selecting 616 the MME includesdetermining whether the eNB 416 is connected to any MMEs that supportthe indicated application category. For example, the eNB 416 maygenerate a list, table, or other data structure that maps connected MMEsto application categories based on the served category parameter 609received during the exchange 608 of S1 setup messages. The eNB 416 maythen refer to the list, table, etc. when determining whether the eNB 416is connected to any MMEs that support the indicated applicationcategory.

Where more than one connected MME supports the indicated applicationcategory, selecting 616 the MME may include selecting one of thesupporting MMEs based on MME capacity, MME overload conditions, or othersuitable criteria. Where no connected MMEs support the indicatedapplication category, the eNB may select an alternative (e.g., nextbest) MME. For example, the eNB 416 may select a MME in a“general-purpose” or “mobile broadband” supporting network slice 145 inresponse to no connecting MMEs supporting aApplicationCategory=Mission-Critical or ApplicationCategory=InfrequentMessaging application category parameter 421. Alternatively, the eNB 416may send an RRC connection reject message indicating that the indicatedapplication category is not supported in response to no connected MMEssupporting the indicated application category.

As illustrated in FIG. 6, the eNB 416 selects the MME-a in the Slice B606 based on the indicated application category. For example, theapplication category parameter 421 may indicate a general-purposeapplication category, which is supported by the Slice B 606. After theeNB 416 selects an MME in an appropriate network slice (here the MME-a)based on the indicated application category, the eNB carries out theknown S1 procedures to connect the UE with the selected MME. Here, theeNB 416 sends an “Initial UE Message” 618 and receives a “DL NASTransport” message in return from the MME in Slice B 606. Thus, the eNB416 attaches the UE 402 to a MME in the appropriate network slice bymatching the application category requested by the UE (in theapplication category parameter 421) with the served category parameter609 received from the connected MMEs.

FIG. 7 illustrates one embodiment of a protocol stack 700 of a remoteunit 105 used for supporting network slicing. In some embodiments, thedepicted protocol stack 700 is a result of the network attach procedures400, 500, and/or 600 used for supporting network slicing. The protocolstack 700 corresponds to a remote unit 105 communicating simultaneouslywith two network slices (e.g., both network slice A 740 and networkslice B 745). In particular, the remote unit 105 has multiple instancesof NAS and RRC radio protocols, each instance corresponding to adifferent network slice 740, 745. Essentially, the remote unit 105 issimultaneously attached to two different packet core instances (e.g. EPCinstances) in the same PLMN.

The protocol stack 700 includes a media access control (“MAC”) sublayerand a physical layer (“PHY”), shown as “MAC/PHY layer” 705. In general,the physical layer 705 serves to generate a radio signal for communicatebits or symbols over a wireless communication link 115. The protocolstack 700 also includes a radio link control (“RLC”) layer 710 incommunication with the physical layer 705. In general, the RLC layer 710transfers protocol data units (“PDUs”) from higher protocol layers,controls PDU segmentation/concatenation and sequencing, and errorcorrection via automatic repeat request (“ARQ”).

The protocol stack 700 further includes a packet data convergenceprotocol (“PDCP”) layer 715 in communication with the RLC layer 710. Ingeneral, the PDCP layer 715 provides header compression/decompression ofIP data and transfers user plane (or control plane) data. The PDCP layer715 communicates control plane data with an RRC layer (e.g., RRC layer720A and/or RRC layer 720B) and communicates user plane data with an IPlayer 735. As depicted, the protocol stack 700 includes one instance foreach of the physical layer 705, the RLC layer 710, the PDCP layer 715,and the IP layer 735.

The protocol stack 700 further includes different instances of radioresource control (“RRC”) layers and non-access stratum (“NAS”) layersfor connections to different network slices. In general, the RRC layermanages establishment, maintenance, and release of an RRC connectionbetween the remote unit 105 and the base unit 110. In general, the NASlayer supports mobility of a remote unit 105 and the session managementprocedures to establish and maintain IP connectivity for the remote unit105.

As depicted, the protocol stack 700 includes a first RRC layer 720A anda first NAS layer 725A associated with a connection to the network sliceA 740. Further, the protocol stack 700 includes a second RRC layer 720Band a second NAS layer 725B associated with a connection to the networkslice B 745. Note that the separate connections to the network slicesare also associated with separate IP addresses (e.g., IP addresses A andB associated with the network slices A and B, respectively).Accordingly, the IP layer 735 and the PDCP layer 715 may communicateusing an IP address for each network slice in communication with thecellular modem 730. While the protocol stack 700 is depicted usingfourth generation (4G) 3GPP LTE radio protocols, the same principlesapply to other radio protocol standards.

FIG. 8 is a schematic flow chart diagram illustrating one embodiment ofa method 800 for supporting network slicing. In some embodiments, themethod 800 is performed by an apparatus, such as the remote unit 105,the user equipment apparatus 200, and/or the UE 402. In certainembodiments, the method 800 may be performed by a processor executingprogram code, for example, a microcontroller, a microprocessor, a CPU, aGPU, an auxiliary processing unit, a FPGA, or the like.

The method 800 may include receiving 805 a data packet to be transmittedvia a mobile communication network, wherein the mobile communicationnetwork supports a plurality of application categories. In oneembodiment, the processor 205 of the user equipment apparatus 200receives the data packet, e.g., from an application running on the userequipment apparatus 200. In another embodiment, the OS 406 receives adata packet from an application 404 running on the UE 402. In certainembodiments, the receiving 805 the data packet includes receiving anetwork connection request. In one embodiment, the network connectionrequest includes an application category parameter.

The method 800 includes identifying 810 an application categoryassociated with the data packet. In one embodiment, the processor 205 ofthe user equipment apparatus 200 identifies 810 the applicationcategory. For example, an application running on the processor 205 mayidentify 810 the application category. In another embodiment, theconnectivity manager 408 and/or the networking layer 502 may identify810 the application category. In certain embodiments, the applicationcategory may be selected from the group consisting of: amission-critical application, an infrequent messaging application, and ageneral-purpose application

In some embodiments, identifying 810 the application category associatedwith the data packet includes applying a category selection policy tothe data packet. The category selection policy may be stored on astorage device, such as the memory 210, and may contain one or morerules for selecting an application category based on data packetcharacteristics. In certain embodiments, the category selection policyis received from an access network discovery and selection function(“ANDSF”) of the mobile telecommunication network.

Where the data packet comprises a network connection request,identifying 810 the application category associated with the networkconnection request may include parsing the network connection requestfor an application category parameter. Additionally, identifying 810 theapplication category may include searching the category selection policyfor a rule specific to the network connection request that overrides theapplication category parameter and identifying an overriding applicationcategory from the overriding rule.

The method 800 includes requesting 815 a network connectioncorresponding to the identified application category. The method 800ends. In one embodiment, the processor 205 of the user equipmentapparatus 200 controls the transceiver 225 to send a network connectionrequest to a base unit 110. In another embodiment, the cellular modem410 (specifically, the RRC layer 414 of the cellular modem 410) may sendan RRC connection message to the eNode B 416. In certain embodiments,requesting 815 a network connection corresponding to the identifiedapplication category includes sending a connection setup message (e.g.,an RRC Connection Setup Complete message) that indicates the identifiedapplication category (e.g., via the application category parameter 421).

In some embodiments, requesting 815 a network connection correspondingto the identified application category includes requesting a connectionto a network slice that supports the identified application category. Incertain embodiments, requesting 815 a network connection correspondingto the identified application category includes communicatingsimultaneously over a plurality of network connections, each networkconnection being to a different network slice of the mobilecommunication network.

In some embodiments, requesting 815 a network connection correspondingto the identified application category includes determining whether anetwork connection corresponding to the identified application categoryexists between the method and the mobile communication network. If anetwork connection corresponding to the identified application categoryalready exists, then requesting 815 the network connection may includethe existing network connection accessing (e.g., requesting access tothe network connection corresponding to the identified applicationcategory). Otherwise, if a network connection corresponding to theidentified application category does not already exist, then requesting815 the network connection may include establishing a new networkconnection with the mobile communication network for the identifiedapplication category.

FIG. 9 is a schematic flow chart diagram illustrating one embodiment ofa method 900 for supporting network slicing. In some embodiments, themethod 900 is performed by an apparatus, such as the remote unit 105,the user equipment apparatus 200, and/or the UE 402. In certainembodiments, the method 900 may be performed by a processor executingprogram code, for example, a microcontroller, a microprocessor, a CPU, aGPU, an auxiliary processing unit, a FPGA, or the like.

The method 900 may include receiving 905 a data packet to be transmittedvia a mobile communication network, the mobile communication networksupporting a plurality of application categories, where the data packetis generated by an application running on the apparatus. In oneembodiment, an application running on the user equipment apparatus 200generates the data packet. In another embodiment, an OS 406 running onthe UE 402 generates the data packet. In certain embodiments, thereceiving 905 the data packet includes receiving a network connectionrequest. In one embodiment, the network connection request includes anapplication category parameter.

The method 900 includes identifying 910 a network slice selectionindicator associated with the data packet. As used herein, a “networkslice selection indicator” refers to an indication used to select aparticular network slice 145 or a category of network slice 145. Oneexample of a network slice selection indicator includes the applicationcategory parameter. In one embodiment, the processor 205 of the userequipment apparatus 200 identifies 910 the application category. Forexample, an application running on the processor 205 may identify 910the network slice selection indicator by identifying an applicationcategory to which the data packet (or application generating the datapacket) belongs. In another example, the connectivity manager 408 and/orthe networking layer 502 may identify 910 the network slice selectionindicator by identifying an application category associated with thedata packet. In certain embodiments, the application category may be amission-critical application, an infrequent messaging application, or ageneral-purpose application

In some embodiments, identifying 910 the network slice selectionindicator associated with the data packet includes applying a categoryselection policy to the data packet. The category selection policy maybe stored on a storage device, such as the memory 210, and may containone or more rules for selecting a network slice selection indicatorbased on data packet characteristics. In certain embodiments, thecategory selection policy is received from an access network discoveryand selection function (“ANDSF”) of the mobile telecommunicationnetwork.

Where the data packet comprises a network connection request,identifying 910 the network slice selection indicator associated withthe network connection request may include parsing the networkconnection request for a selection parameter, such as an applicationcategory parameter. Additionally, identifying 910 the applicationcategory may include searching the category selection policy for a rulespecific to the network connection request that overrides theapplication category parameter included in the network connectionrequest and identifying an overriding application category from theoverriding rule.

The method 900 includes transmitting 915 the data packet using a networkconnection to a network slice in the mobile communication network, saidnetwork connection associated with the identified network sliceselection indicator. The method 900 ends. In one embodiment, theprocessor 205 controls the transceiver 225 to send the data packet.

In some embodiments, transmitting 915 the data packet using a networkconnection associated with the identified network slice selectionindicator includes determining whether a network connection associatedwith the identified network slice selection indicator exists between theapparatus and the mobile communication network. If such a networkconnection already exists, then the data packet is sent over theexisting network connection. Otherwise, if a network connectionassociated with the network slice selection indicator does not alreadyexist between the apparatus and the mobile communication network, thentransmitting 915 the data packet includes establishing a new networkconnection with the indicated network slice and transmitting the datapacket comprises transmitting via the new network connection.

FIG. 10 is a schematic flow chart diagram illustrating one embodiment ofa method of a base unit for supporting network slicing. In someembodiments, the method 1000 is performed by an apparatus, such as thebase unit 110, the base station apparatus 300, and/or the eNB 416. Incertain embodiments, the method 1000 may be performed by a processorexecuting program code, for example, a microcontroller, amicroprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, orthe like.

The method 1000 begins with receiving 1005, e.g., from a remote unit, arequest to establish a network connection with a mobile communicationnetwork, wherein the mobile communication network includes a pluralityof application categories. In one embodiment, the radio transceiver 325of the base station apparatus 300 receives a network connection request.

The method 1000 includes identifying 1010 a network slice selectionindicator associated with the request. In one embodiment, the processor305 of the base station apparatus 300 identifies 810 the network sliceselection indicator, for example from an RRC connection setup message ofthe network connection request.

The method 1000 includes selecting 1015 a management function in anetwork slice that supports the network slice selection indicator. Insome embodiments, selecting 1015 the management function in a networkslice based on the network slice selection indicator includesidentifying a network slice 145 that supports an application categoryindicated in the network slice selection indicator. In variousembodiments, the application category is selected from the groupconsisting of: a mission-critical application, an infrequent messagingapplication, and a general-purpose application.

In some embodiments, the apparatus has pre-established a signalingconnection with a management function in each network slice, eachmanagement function (or network slice) being associated with a traffictype. Here, selecting 1015 the management function in a network slicebased on the network slice selection indicator includes matching thenetwork slice selection indicator to a network slice using the traffictype associated with the management function in a network slice.

The method 1000 includes establishing 1020 the requested connection byusing the selected management function in the network slice. The method1000 ends. In various embodiments, establishing 1020 the requestedconnection by using the selected management function in the selectednetwork slice comprises sending an initial UE message to the selectedmanagement function and receiving a downlink NAS transport message fromthe selected management function.

FIG. 11 is a schematic flow chart diagram illustrating one embodiment ofa method of a remote unit for selecting a network slice, e.g., in amobile communication network. In some embodiments, the method 1100 isperformed by an apparatus, such as the remote unit 105, the userequipment apparatus 200, and/or the UE 402. In certain embodiments, themethod 1000 may be performed by a processor executing program code, forexample, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliaryprocessing unit, a FPGA, or the like.

The method 1100 begins with receiving 1105, e.g., at a remote unit, arequest to send a data packet, wherein the data packet is generated byan application of the remote unit. In some embodiments, receiving 1105the request to send the data packet includes receiving a networkconnection request that contains an application category parameter.

In some embodiments, receiving 1105 the request to send the data packetcomprises receiving a network connection request that contains a networkcapability parameter. In some embodiments, receiving the request to sendthe data packet comprises receiving a network connection request thatcontains a transport type parameter. In certain embodiments, thetransport type parameter indicates one or more of: an access networktype, a virtual private network, a transport protocol, and a modem type.

The method 1100 includes identifying 1110 a network slice selectionindicator associated with the application of the remote unit. In someembodiments, identifying the network slice selection indicatorassociated with the application comprises verifying the applicationcategory parameter using a selection policy. In one embodiment,verifying the application category parameter using a selection policyincludes determining whether the application is permitted to use anetwork slice associated with the application category parameter.

In some embodiments, the remote unit receives a selection policy fromthe mobile communication network, the selection policy being stored atthe remote unit and comprising a plurality of rules for selecting anetwork slice based on the application. In such embodiments, identifying1110 the network slice selection indicator associated with theapplication includes applying the selection policy to the application.

In some embodiments, identifying 1110 the network slice selectionindicator associated with the application includes applying a selectionpolicy to the network capability parameter to select the network sliceselection indicator. In some embodiments, identifying 1110 the networkslice selection indicator associated with the application includesapplying a selection policy to the transport type parameter to selectthe network slice selection indicator.

The method 1100 includes transmitting 1115 the data packet via a networkconnection to a network slice in a mobile communication network. Here,the mobile communication network supports a plurality of network slicesand the network connection is associated with the identified networkslice selection indicator. The method 1100 ends. In one embodiment, thenetwork connection to a network slice in the mobile communicationnetwork comprises a connection to a network slice that supports atraffic type associated with the application.

In some embodiments, transmitting 1115 the data packet via the networkconnection to the network slice includes: determining whether a networkconnection associated with the identified network slice selectionindicator exists between the remote unit and the mobile communicationnetwork, transmitting the data packet via an existing network connectionin response to determining that a network connection associated with thenetwork slice selection indicator exists between the remote unit and themobile communication network, and establishing a new network connectionwith the identified network slice selection indictor for transmittingthe data packet in response to determining that a network connectionassociated with the network slice selection indicator does not existbetween the remote unit and the mobile communication network.

Embodiments may be practiced in other specific forms. The describedembodiments are to be considered in all respects only as illustrativeand not restrictive. The scope of the invention is, therefore, indicatedby the appended claims rather than by the foregoing description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

The invention claimed is:
 1. An apparatus comprising: a transceiver thatcommunicates with a mobile communication network supporting a pluralityof network slices; and a processor that: receives a request to send adata packet, wherein the data packet is generated by an application ofthe apparatus; identifies a network slice selection indicator associatedwith the application of the apparatus; and transmits the data packet viaa network connection to a network slice in the mobile communicationnetwork, wherein the network connection is associated with theidentified network slice selection indicator.
 2. The apparatus of claim1, wherein transmitting the data packet via the network connection tothe network slice comprises the processor: determining whether a networkconnection associated with the identified network slice selectionindicator exists between the apparatus and the mobile communicationnetwork; transmitting the data packet via an existing network connectionin response to determining that a network connection associated with thenetwork slice selection indicator exists between the apparatus and themobile communication network; and establishing a new network connectionwith the identified network slice selection indictor for transmittingthe data packet in response to determining that a network connectionassociated with the network slice selection indicator does not existbetween the apparatus and the mobile communication network.
 3. Theapparatus of claim 1, wherein the processor further receives a selectionpolicy from the mobile communication network, the selection policy beingstored at the apparatus and comprising a plurality of rules forselecting a network slice based on the application, wherein identifyingthe network slice selection indicator associated with the applicationcomprises the processor applying the selection policy to theapplication.
 4. The apparatus of claim 1, wherein receiving the requestto send the data packet comprises receiving a network connection requestthat contains an application category parameter, wherein identifying thenetwork slice selection indicator associated with the applicationcomprises verifying the application category parameter using a selectionpolicy.
 5. The apparatus of claim 4, wherein the application categoryparameter indicates a category selected from the group consisting of: amission-critical application, an infrequent messaging application, and ageneral-purpose application.
 6. The apparatus of claim 4, whereinverifying the application category parameter comprises determiningwhether the application is permitted to use a network slice associatedwith the application category parameter.
 7. The apparatus of claim 1,wherein the network connection to the network slice in the mobilecommunication network comprises a connection to a network slice thatsupports a traffic type associated with the application.
 8. Theapparatus of claim 1, wherein receiving the request send the data packetcomprises receiving a network connection request that contains a networkcapability parameter, wherein identifying the network slice selectionindicator associated with the application comprises applying a selectionpolicy to the network capability parameter to select the network sliceselection indicator.
 9. The apparatus of claim 1, wherein receiving therequest to send the data packet comprises receiving a network connectionrequest that contains a transport type parameter, wherein identifyingthe network slice selection indicator associated with the applicationcomprises applying a selection policy to the transport type parameter toselect the network slice selection indicator.
 10. The apparatus of claim9, wherein the transport type parameter indicates one or more of: anaccess network type, a virtual private network, a transport protocol,and a modem type.
 11. A method comprising: receiving, at a remote unit;a request to send a data packet, wherein the data packet is generated byan application of the remote unit; identifying a network slice selectionindicator associated with the application of the remote unit; andtransmitting the data packet via a network connection to a network slicein a mobile communication network, said mobile communication networksupporting a plurality of network slices, wherein the network connectionis associated with the identified network slice selection indicator. 12.The method of claim 11, wherein transmitting the data packet via thenetwork connection to the network slice comprises: determining whether anetwork connection associated with the identified network sliceselection indicator exists between the remote unit and the mobilecommunication network; transmitting the data packet via an existingnetwork connection in response to determining that a network connectionassociated with the network slice selection indicator exists between theremote unit and the mobile communication network; and establishing a newnetwork connection with the identified network slice selection indictorfor transmitting the data packet in response to determining that anetwork connection associated with the network slice selection indicatordoes not exist between the remote unit and the mobile communicationnetwork.
 13. The method of claim 11, further comprising: receiving aselection policy from the mobile communication network, the selectionpolicy being stored at the remote unit and comprising a plurality ofrules for selecting a network slice based on the application, whereinidentifying the network slice selection indicator associated with theapplication comprises applying the selection policy to the application.14. The method of claim 11, wherein receiving the request to send thedata packet comprises receiving a network connection request thatcontains an application category parameter, wherein identifying thenetwork slice selection indicator associated with the applicationcomprises verifying the application category parameter using a selectionpolicy.
 15. The method of claim 14, wherein the application categoryparameter indicates a category selected from the group consisting of: amission-critical application, an infrequent messaging application, and ageneral-purpose application.
 16. The method of claim 14, whereinverifying the application category parameter using a selection policycomprises determining whether the application is permitted to use anetwork slice associated with the application category parameter. 17.The method of claim 11, wherein the network connection to the networkslice in the mobile communication network comprises a connection to anetwork slice that supports a traffic type associated with theapplication.
 18. The method of claim 11, wherein receiving the requestto send the data packet comprises receiving a network connection requestthat contains a network capability parameter, wherein identifying thenetwork slice selection indicator associated with the applicationcomprises applying a selection policy to the network capabilityparameter to select the network slice selection indicator.
 19. Themethod of claim 11, wherein receiving the request to send the datapacket comprises receiving a network connection request that contains atransport type parameter, wherein identifying the network sliceselection indicator associated with the application comprises applying aselection policy to the transport type parameter to select the networkslice selection indicator.
 20. The method of claim 19, wherein thetransport type parameter indicates one or more of: an access networktype, a virtual private network, a transport protocol, and a modem type.